Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1224

reference
738-tree-1
name
1224
tree-preservation-order

undefined

738-tpo-1
uprn
address-text
point
POINT (-1.008293 50.886368)
geometry
MULTIPOLYGON (((-1.008237 50.886362,-1.008239 50.886373,-1.008247 50.886383,-1.008260 50.886391,-1.008275 50.886396,-1.008293 50.886398,-1.008310 50.886396,-1.008326 50.886391,-1.008339 50.886384,-1.008347 50.886374,-1.008350 50.886363,-1.008348 50.886351,-1.008340 50.886341,-1.008328 50.886333,-1.008312 50.886328,-1.008294 50.886326,-1.008277 50.886328,-1.008261 50.886333,-1.008248 50.886341,-1.008240 50.886350,-1.008237 50.886362)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL